> > Whatever brilliant boy first implemented file access via FTP in a web browser > should be taken out and beaten soundly about the noggin with rolled-up RFCs. > It maintains the one-connection-per-item paradigm, which is NOT the way FTP > works, and everybody since then copied the method without THINKING first. > > Thus, if you're logging FTP connections, you get six times more NOISE than > necessary when some point-and-click lamer wants ONE lousy file. Not to > mention twice as much TCP setup overhead. > > How hard would it be, once a browser realizes that it's talking to an FTP > server, to just keep the control socket open?! It's probably way too late to > get it fixed by now, dammit. > > _H* You should ALWAYS go through a caching proxy like cern_httpd. Not only does it cache data for repeated access, it caches connections to servers for ftp, http (I think), etc. sdw -- Stephen D. Williams 25Feb1965 VW,OH sdw@lig.net http://www.lig.net/sdw Senior Consultant 513-865-9599 FAX/LIG 513.496.5223 OH Page BA Aug94-Feb95 OO R&D AI:NN/ES crypto By Buggy: 2464 Rosina Dr., Miamisburg, OH 45342-6430 Firewall/WWW srvrs ICBM/GPS: 39 38 34N 84 17 12W home, 37 58 41N 122 01 48W wrk Pres.: Concinnous Consulting,Inc.;SDW Systems;Local Internet Gateway Co.28Jan95